Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0444

reference: 192-tree-1
name: 0444
tree-preservation-order: undefined
192-tpo-1
uprn
address-text
point: POINT (-0.940748 50.861998)
geometry: MULTIPOLYGON (((-0.940677 50.861990,-0.940680 50.862004,-0.940690 50.862017,-0.940706 50.862027,-0.940725 50.862034,-0.940747 50.862036,-0.940769 50.862034,-0.940789 50.862028,-0.940805 50.862018,-0.940815 50.862006,-0.940819 50.861992,-0.940816 50.861978,-0.940806 50.861965,-0.940791 50.861955,-0.940771 50.861949,-0.940749 50.861946,-0.940727 50.861948,-0.940707 50.861954,-0.940691 50.861964,-0.940681 50.861977,-0.940677 50.861990)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL